Google API Policy

Last Updated: August 17, 2025

Website: alwaysonplanb.com

Our Commitment to Google API Compliance

alwaysonplanb.com strictly adheres to Google's API Services User Data Policy and Limited Use requirements for all applications that access Google user data.

Limited Use Compliance

Our applications comply with Google's Limited Use requirements:

Data Use Restrictions

We DO NOT:

  • • Use user data to develop, improve, or train generalized AI and/or ML models
  • • Allow humans to read user data unless specific user consent is obtained
  • • Use or transfer data for serving advertisements
  • • Use data for purposes unrelated to core application functionality

Permitted Uses

We ONLY use Google user data to:

  • • Provide user-facing features prominently displayed in our applications
  • • Enhance functionality directly related to the stated purpose
  • • Maintain security and prevent abuse
  • • Comply with applicable laws and legal processes

Gmail™ API Compliance

For Smart Delete for Gmail™:

Data Access

  • Email metadata (sender, subject, date) for rule creation only
  • Email content solely for pattern recognition and user-authorized actions
  • No content storage beyond temporary processing requirements

User Control

  • • Users explicitly authorize all email deletion operations
  • • Preview functionality shows exactly what will be deleted
  • • Users can revoke access at any time by uninstalling the application

Security Measures

  • • All processing occurs within Google's secure infrastructure
  • • No email data is transferred to external servers
  • • Encryption in transit and at rest follows Google's standards

Apps Script Platform Compliance

Our Google Apps Script applications:

  • • Operate entirely within Google's secure environment
  • • Use only Google-provided APIs and services
  • • Store user data exclusively in Google's property stores
  • • Follow Google's best practices for add-on development

Scope Justifications

Gmail Read Scope

Purpose: Read email metadata (sender, subject, date, labels) to identify patterns for deletion rules

Justification: Essential for pattern recognition on email metadata (sender, subject, date) to identify promotional emails and generate safety previews showing users exactly which emails will be affected before any action.

User Benefit: Enables smart pattern recognition to suggest relevant cleanup rules based on user's actual email patterns

User Control: Users see preview of emails matching rules before any deletion occurs

Why narrower scopes insufficient: gmail.metadata lacks access to full sender information and labels needed for effective pattern matching

Gmail Modify Scope

Purpose: Move emails to Trash folder based on user-created and user-authorized deletion rules/jobs

Justification: Required to execute user-authorized trash operations after explicit user confirmation.

User Benefit: Core functionality - enables bulk email cleanup as requested by users

Control: User is in full control of deletions. Emails moved to Trash (recoverable for 30 days), never permanently deleted

Why narrower scopes insufficient: gmail.readonly cannot perform deletions; gmail.send is unrelated to our functionality

Script Container UI Scope

Purpose: Provide add-on interface within Gmail

Justification: Required for Google Workspace Add-on functionality. Essential for providing in-context email management tools within Gmail interface.

User Benefit: Seamless integration with Gmail interface

User Control: Only operates when user explicitly authorizes actions through the add-on interface

Why narrower scopes insufficient: Essential for Gmail add-on functionality - no narrower alternative available for Apps Script add-ons

Data Minimization

We implement data minimization by:

  • • Accessing only necessary scopes for functionality
  • • Processing minimal data required for features
  • • Automatically deleting temporary processing data
  • • Avoiding data collection for non-essential purposes

Security Safeguards

Technical Measures

  • • Industry-standard encryption for all data transmission
  • • Secure authentication using Google OAuth 2.0
  • • Regular security assessments and updates
  • • Access controls limiting data exposure

Operational Measures

  • • Staff training on data protection requirements
  • • Incident response procedures for security events
  • • Regular compliance audits and reviews
  • • Vendor assessments for any third-party services

Contact for API Compliance

For questions about our Google API compliance:

Website: alwaysonplanb.com

Email: alwaysonplanb@gmail.com

Developer: Venkata P

Regulatory References

This compliance statement addresses requirements from:

  • • Google API Services User Data Policy
  • • Google OAuth 2.0 Policies
  • • Google Workspace Marketplace Developer Policies
  • • EU General Data Protection Regulation (GDPR)
  • • California Consumer Privacy Act (CCPA)

Gmail™ is a trademark of Google LLC.